✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@seanconroy2021 this PR isn't even updating the utils image to the same image. For example, if I click the files changed tab, I see two different refs within the first file. Is that expected?

@seanconroy2021 this PR isn't even updating the utils image to the same image. For example, if I click the files changed tab, I see two different refs within the first file. Is that expected?

Looks like each utils image reference is treated as its own dependency, so Mint is updating them independently, which doesn't seem the best. We should be able to group them so we can update all of them with one digest. Will take a look.

@seanconroy2021 this PR isn't even updating the utils image to the same image. For example, if I click the files changed tab, I see two different refs within the first file. Is that expected?

Looks like each utils image reference is treated as its own dependency, so Mint is updating them independently, which doesn't seem the best. We should be able to group them so we can update all of them with one digest. Will take a look.

great, thank you

great, thank you

I can't seem to find any Renovate config to force all digest refs to update to the same target digest using the Tekton manager. Maybe @lubomir might have some ideas?

Did you mean to ping someone else, @seanconroy2021 ? I have no idea about any of this.

Did you mean to ping someone else, @seanconroy2021 ? I have no idea about any of this.

Yeah sorry wrong person :(

great, thank you

I can't seem to find any Renovate config to force all digest refs to update to the same target digest using the Tekton manager. Maybe @lubomir might have some ideas?

@querti ^^

Checking the digests, my guess is that if an image was specified via single arch digest, renovate will propose an update to a newer single arch, and likewise for multiarch. I don't know the reason for specifying a specific arch to run certain steps, but if the reason is legitimate then the behavior seems correct to me. If there is no good reason for this then I suggest specifying multiarch digest for all tasks and all images will be updated to the same digest in the future.

Checking the digests, my guess is that if an image was specified via single arch digest, renovate will propose an update to a newer single arch, and likewise for multiarch. I don't know the reason for specifying a specific arch to run certain steps, but if the reason is legitimate then the behavior seems correct to me. If there is no good reason for this then I suggest specifying multiarch digest for all tasks and all images will be updated to the same digest in the future.

I would think we should be using the same arch setting imageRef for all of our tasks. So what do we do with this PR?

We can request a rebase after we've unified the digests. Or I think it should be safe to merge it as-is, if we want to update the image asap.

Checking the digests, my guess is that if an image was specified via single arch digest, renovate will propose an update to a newer single arch, and likewise for multiarch. I don't know the reason for specifying a specific arch to run certain steps, but if the reason is legitimate then the behavior seems correct to me. If there is no good reason for this then I suggest specifying multiarch digest for all tasks and all images will be updated to the same digest in the future.

From what I know we don't release single-arch images it's grouped as multi-arch when pushed to Quay. Unless Renovate is handling this differently than expected. If these tasks were single-arch digest, they probably would fail when run locally on Kind for ARM64 (MAC) which they don't. So there might be something else going on here?

Checking the digests, my guess is that if an image was specified via single arch digest, renovate will propose an update to a newer single arch, and likewise for multiarch. I don't know the reason for specifying a specific arch to run certain steps, but if the reason is legitimate then the behavior seems correct to me. If there is no good reason for this then I suggest specifying multiarch digest for all tasks and all images will be updated to the same digest in the future.

From what I know we don't release single-arch images it's grouped as multi-arch when pushed to Quay. Unless Renovate is handling this differently than expected. If these tasks were single-arch digest, they probably would fail when run locally on Kind for ARM64 (MAC) which they don't. So there might be something else going on here?

Yeah I have no idea, but I'm moving this to draft. The images aren't consistent and the unit tests are failing anyways